[HUDI-5271] fix issue inconsistent reader and writer schema in HoodieAvroDataBlock#7297
Closed
TengHuo wants to merge 1 commit intoapache:masterfrom
Closed
[HUDI-5271] fix issue inconsistent reader and writer schema in HoodieAvroDataBlock#7297TengHuo wants to merge 1 commit intoapache:masterfrom
TengHuo wants to merge 1 commit intoapache:masterfrom
Conversation
…AvroDataBlock Co-authored-by: voonhous <voonhousu@gmail.com>
TengHuo
changed the title
This was referenced Nov 24, 2022
Collaborator
Contributor
Author
|
Close this PR as it is outdated. |
Contributor
Author
|
New PR for fix the issue: #7307 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Trouble shooting detail in issue: #7284
Change Logs
HoodieBaseRelation#convertToAvroSchemafor generating a record name and space name for Avro schemaTestMorTablefor verifying the issue is fixedImpact
No public API changed, but need to check if this fix can work with the feature Schema Evolution properly.
Risk level (write none, low medium or high below)
low
Documentation Update
No doc or configuration changed.
Contributor's checklist